-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: improve gno linter with basic errors support #1202
Conversation
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
from `testscripts` doc.go: UpdateScripts specifies that if a `cmp` command fails and its second argument refers to a file inside the testscript file, the command will succeed and the testscript file will be updated to reflect the actual content (which could be stdout, stderr or a real file). The content will be quoted with txtar.Quote if needed; a manual change will be needed if it is not unquoted in the script. Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1202 +/- ##
==========================================
+ Coverage 55.95% 56.05% +0.10%
==========================================
Files 435 435
Lines 66306 66409 +103
==========================================
+ Hits 37101 37228 +127
+ Misses 26303 26287 -16
+ Partials 2902 2894 -8
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
0297418
to
5eb43c4
Compare
Signed-off-by: gfanton <[email protected]>
Related with #1215. |
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a test that makes sure that the preprocess stack is still printed in other places (ie. a normal stacktrace?)
thx
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you add an example in CONTRIBUTING.md to use it with your editor?
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
Signed-off-by: gfanton <[email protected]>
@moul added integration for emacs + vim (Im not sure this is the usual way for the last one, but at last it works) |
I've improved the linter by using
RunMemPackage
in the same way thatgno test
does for testing.A direct use case for this PR is to provide a simple and reliable method for editors to integrate
gno linting
.(There might be a better way to achieve what I've done, of which I'm not aware)
Below a sample of
gno lint
output:And here's a brief demo using basic integration with emacs:
Contributors' checklist...
BREAKING CHANGE: xxx
message was included in the description